Access monitoring system for compliance

ABSTRACT

The present invention provides a system for compliance monitoring of vehicles and users of hydrocarbon wellsites and method of use. The system includes at least one portable access control station located in the monitored hydrocarbon wellsite and a system server at a monitoring center. The system server is configured to be in communication with the portable access control station via a network. The portable access control station includes a checkpoint monitor and an access control unit. The portable access control station is configured to monitor vehicle and personnel access related events in the hydrocarbon wellsite and send data related to the events to the system server.

RELATED APPLICATIONS

This application is a Continuation in Part of U.S. patent applicationSer. No. 15/846,194 filed Dec. 18, 2017, which is a Continuation of U.S.patent application Ser. No. 15/461,831 filed Mar. 17, 2017, which is aContinuation-in-Part of U.S. patent application Ser. No. 14/737,518filed on Jun. 12, 2015, which claims priority from Provisional PatentApplication Ser. No. 62/011,156 filed on Jun. 12, 2014, all of which areexpressly incorporated by reference herein in their entirety.

BACKGROUND Field of the Invention

The present invention relates generally to electronic access systemsand, more particularly, to methods and systems for monitoring access tofenced or unfenced remote locations, fields or outdoor sites such as,without limitation, hydrocarbon recovery locations, well sites or anyland or offshore based hydrocarbon recovery facilities

Description of the Related Art

Industrial companies can have remote production facilities in remoteenvironments. Such remote facilities can use manufacturing equipment,machines and systems to perform various operational stages of a plannedwork including building, preparation, production or maintenance.Depending on the work, the work schedules in such remote facilities canbe continuous, a year around fashion, or seasonal, which are followed byoperators or work crews assigned to the remote facility.

For example, hydrocarbon recovery or production fields, such as for oilor natural gas production, are often located in remote locations andinclude equipment such as drilling rigs, pumps and other relatedequipment and machinery. The equipment in such remote fields is mostoften attended by on-site machine operators or crews whom actuallyoperate or maintain the equipment, although the company owning thefacility is located in a city often hundreds of miles away.

During an active operation cycle, the operators generally can operatethe equipment such as the drilling equipment. However, if the operationis not a day-to-day activity, for example, a post drilling work activityinvolving hydrocarbon recovery using pumps and storage tanks, amaintenance operator or a maintenance crew can visit the facilityperiodically to observe the operation in the facility.

In either case, in the instances, for example, where the facilityexperiences a problem, the operator must then solve the problem or alertthe company for help. The problem can be related to the machinerymalfunction, vandalism or natural catastrophe related given the remotenature of the facility.

In today's economy, the lost productivity and opportunity due tounwanted down time generated by such problems can be extremely costly ifa service crew or engineer is not dispatched on time to the remote siteof the facility by the company.

Therefore, it is important for the company to monitor the activity ofthe operators on the remote site to reduce the amount of facility downtime to a minimum while increasing reliance by getting instantly updatedabout problems, changes or modifications in the facility. It is alsoimportant for the company to remotely monitor access of vehicles intoand out of the remote site and collect information related to vehicleactivity in the remote field.

Thus, from the foregoing, there is an unaddressed need exists for anovel system and method in the industry to address the aforementioneddeficiencies quickly and efficiently.

SUMMARY

An aspect of the present invention includes a system for compliancemonitoring of vehicles and users of hydrocarbon wellsites, the systemincludes: a system server including a system data storage and a systemprocessor; a portable access control station located in a hydrocarbonwellsite which is a compliance monitored hydrocarbon wellsite andremotely located from the system server; a checkpoint monitor of theportable access control station, the checkpoint monitor including aserver having a data storage and a processor in communication with thesystem processor; an access control unit of the portable access controlstation, the access control unit being in communication with the serverof the checkpoint monitor and including vehicle sensors to detectvehicles, a barrier drive which is movably coupled to a vehicle barrier,and a controller configured to be in connection with the processor ofthe server, the vehicle sensors and the barrier drive, the controllerbeing configured to operate the barrier drive for pivoting the vehiclebarrier between a blocking position and an open position; wherein uponreceiving vehicle sensor data from the vehicle sensors indicating thepresence of a vehicle, the processor analyzes an access code receivedfrom an access code provider to authenticate a user in the vehicle andsignal the controller of the access control unit to move the vehiclebarrier into the open position to allow the vehicle to enter thehydrocarbon wellsite when the user is successfully authenticated, andwherein the access code includes a user ID code and a user activitycode.

Another aspect of the present invention includes a method for compliancemonitoring of vehicles and users of hydrocarbon wellsites, including:providing a system server in a monitoring center, the system serverincluding a system processor and a system data storage including anassignment data table for the monitored location and a system programthat when executed causes the system processor to operate the system,wherein the assignment data table includes user assignment status dataand user activity status data; installing a checkpoint monitor on aperimeter of a hydrocarbon wellsite which is compliance monitored andremotely located from the system server, the checkpoint monitorincluding a processor and a data storage including the assignment datatable received from the system server and a program that when executedcauses the processor to operate the checkpoint monitor; installing anaccess control unit adjacent the checkpoint monitor, the access controlunit including vehicle sensors to detect vehicles, a barrier drive whichis movably coupled to a vehicle barrier, and a controller being inconnection with the processor of the checkpoint monitor, the vehiclesensors and the barrier drive; detecting a vehicle with the vehiclesensors of the access control unit; receiving, in the checkpointmonitor, vehicle sensor data from the access control unit indicatingpresence of a vehicle; receiving, in the checkpoint monitor, an accesscode from an access code provider operated by a user associated with thevehicle; analyzing with the processor the access code received from theaccess code provider to authenticate the user associated with thevehicle; pivoting the vehicle barrier from a blocking position to anopen position using the barrier drive to allow the vehicle to enter thehydrocarbon wellsite upon successfully authenticating the userassociated with the vehicle; receiving, in the checkpoint monitor,vehicle sensor data from the access control unit indicating absence of avehicle; and pivoting the vehicle barrier from the open position to theblocking position using the barrier drive.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other aspects and features of the present invention willbecome apparent to those of ordinary skill in the art upon review of thefollowing description of specific embodiments of the invention inconjunction with the accompanying figures, wherein:

FIG. 1 is a schematic view of an embodiment of an exemplaryimplementation of a monitoring system of the present invention;

FIGS. 2A-2B are schematic side and top views of an embodiment of acheckpoint monitor device of the monitoring system of the presentinvention;

FIG. 3 is a schematic diagram illustrating an exemplary embodiment ofthe monitoring system;

FIG. 4 is a schematic block diagram illustrating an embodiment of acheckpoint monitor device with a checkpoint server, a data storage andexemplary modules employed during compliance monitoring of users;

FIG. 5 is a schematic block diagram illustrating an embodiment of asystem server operating the monitoring system of the present invention;

FIG. 6 is a schematic view of an assignment data table for a monitoredlocation, the assignment data table including assignment status data andactivity status data;

FIGS. 7A-7B are schematic views of the assignment data table stored inthe system server's database and the checkpoint monitors' data basesrespectively;

FIG. 8 is a schematic flow chart illustrating an embodiment of anexemplary operation sequence implemented in the monitoring system of thepresent invention;

FIG. 9 is an exemplary embodiment of an algorithm performed by acheckpoint monitor to determine the assignment status and the activitystatus of the users;

FIG. 10 is a schematic flow chart illustrating an embodiment of anexemplary operation sequence implemented in the system of the presentinvention;

FIGS. 11A-11D are schematic flow charts illustrating embodiments ofexemplary operation sequences implemented in the system of the presentinvention;

FIG. 12A is a schematic diagram illustrating an embodiment of thecompliance monitoring system;

FIG. 12B is a schematic view of an embodiment of an exemplaryimplementation of the compliance monitoring system of the presentinvention;

FIG. 13 is a schematic illustration of an embodiment of an accesscontrol station of the present invention;

FIGS. 14A-14C are schematic illustrations of exemplary access codeproviders used with the access control station;

FIGS. 15A-15B are schematic illustrations of base components used withthe access control station;

FIG. 16 is a schematic view of an embodiment of a compliance monitoringsystem including the access control station;

FIGS. 17A-17C illustrate an exemplary embodiment of a method of thepresent invention; and

FIG. 18 illustrates a schematic flow chart of an embodiment of anexemplary operation sequence implemented in the compliance monitoringsystem of the present invention;

DETAILED DESCRIPTION OF THE EMBODIMENTS

Unlike office buildings or large plants in urban areas with walls,fences and gates, remote oilfield worksites or work locations haveporous and loosely defined perimeters. It is often a challenge for theoil companies to ensure safety and security of the personnel working insuch remote worksites in oilfields. Personnel may enter and leave suchworksites without being accounted for. In one embodiment, the presentinvention may solve this problem by introducing voluntary checkpoints,monitoring and identifying noncompliant entries and exits; then,resolving such noncompliant events to obtain an accurate headcount ofthe personnel on such remote worksites in oilfields, thereby increasingsafety and security of the personnel in such locations. Embodiments ofthe present invention may provide systems that may enforce time andattendance compliance by way of monitoring the activity of authorizedemployees or users of remote locations. By tracking employee compliancewith scheduled work assignments, for example, in remote hydrocarbonfields, such as oilfields, employer organizations may achieve highemployee time and attendance compliance levels in such environments,which may reduce maintenance and production cost while increasingproductivity.

In one embodiment, the present invention provides a system and a methodthat address the monitoring of employee compliance at remote work sitessuch as hydrocarbon recovery or production fields for oil or natural gasproduction or recovery. This embodiment will be described below withrespect to FIGS. 1-11D. The system may collect employee access activitydata from small footprint by rapidly deployable electronic checkpointmonitor devices placed around the monitored locations and theirsublocations, creating a virtual or electronic fence for each location.Such collected data from all the checkpoint monitors is then transmittedto a central monitoring server or system server where the collected datais integrated, analyzed and presented to the location administratorswith activity reports and visual confirmation of every event, and thelike. The system and method of the invention may track employeeactivities and allow for remote visual monitoring of the remote worksites for client organizations. The monitoring system may furtherutilize a wide area network, including routers, servers and software toprovide real-time compliance monitoring of employees and other personnelof the remote worksites, along with visual monitoring of the remote worksite.

By ensuring compliance with assignment schedules, some of the additionalbenefits of the system of the present invention may be as follows: (1)minimizing or preventing equipment breakdowns and the resultingdowntime; (2) ensuring equipment reliability; (3) ensuring timelyrepairs to equipment; (4) ensuring application of organization policyand procedures in remote work environments; (5) improving employeesafety in such fields; (6) aligning payroll costs with the hoursactually worked; (7) reducing administrative time in managing suchremote fields; (8) reducing time spent on the administrative auditsrelated to employee time and attendance for compliance; (9) providingasset protection and theft prevention benefits by deterring unauthorizedentries, thereby reducing theft and potential safety issues; (10)providing verifiable data for the third party invoice approvals byproviding access to past check-in and check-out data to verify theaccuracy of the invoicing; (11) providing crew management benefits byproviding instant visibility to the crew locations and observing theiractivities when onsite supervision is not readily available; (12)providing safety benefits by observing safety violations of unsupervisedcrews and promoting compliance; and (13) providing cost benefits bypotentially reducing insurance premiums.

In another embodiment, the compliance monitoring system of the presentinvention may include an access control station including an accesscontrol unit in connection with a checkpoint monitor to further monitorvehicles and users of the compliance monitored field. This embodimentwill be described below with respect to FIGS. 12A-18.

FIG. 1 shows an exemplary monitoring system 100 of the present inventionrelated to an exemplary map view of a location 101, or a field, such asa hydrocarbon field for oil or natural gas production or recovery. Terms“location” or “field” may refer to remote location, remote field, remotesite, site, area, work location, work field, worksite, work area,oilfield, oilsite, wellsite and the like. The monitoring system 100comprises one or more checkpoint monitors (CM) 102 that are incommunication with a system server 103 which may be, in turn, incommunication with a client interface 104. The system server 103 may belocated in a monitoring center of a monitoring company and may beconfigured to communicate with the checkpoint monitors in the monitoredfield and with the client organizations via client interfaces 104 overone or more communication networks 120, such as one or more wide areanetworks 120, i.e., computer networks, the Internet, telephone networks,and the like. Using the checkpoint monitors 102, the system 100 mayprovide real time compliance monitoring of the users or employees at themonitored location 101 and report the collected data to the clientorganizations via the monitoring center server 103.

In one embodiment, an exemplary compliance monitoring using thecheckpoint monitors 102 of the system 100 may be performed to obtainuser related information such as at least one of the user assignmentstatus and the user activity status of the user associated with thelocation 101. The location 101 may be defined by a geographicalperimeter 105 which may be fenceless or fenced. In this application, afenceless location may define a location with highly porous borders,which may not have a visible and/or physically protruding fencestructure surrounding at least a portion of the monitored location, andwhich may not have any invisible and/or non-protruding structuresurrounding at least a portion of the monitored location, such as aburied sensor line or a system providing an invisible detection networkaround or over the monitored location. There may also be one or morework locations or worksites within the location 101, such as a firstwork location 106A, or a first location, including for example oilpumps, and a second work location 106B, or a second location, includingfor example a drilling rig and related equipment and storage facilities.The first and second work locations 106A and 106B may have geographicalperimeters 108A and 108B respectively, which may be fenceless or fenced.One or more checkpoint monitors 102, such as 102A, 102B, 102C, 102D and102E may be installed along the perimeter 105 of the location 101 and,optionally, along the perimeters 108A and 108B of the first and secondwork locations 106A and 106B respectively. The checkpoint monitors 102may be in communication with the system server 103 in a remote managingfacility. As will be described more fully below, each checkpoint monitor102 in the location 101 may be surrounded by a checkpoint zone Z.Checkpoint zones Z, such as Z1, Z2, Z3, Z4 and Z5 may be defined ascircular areas or cylindrical space around each checkpoint monitors 102.

The geographical perimeters 108A and 108B of the first and second worklocations 106A and 106B may be nested in the geographical perimeter 105of the location 101. Thus, the first and second locations 106A and 106Bmay be defined as sublocations of the location 101 which may be definedas a higher status location, or higher location, with respect to thenested smaller sublocations. When there is at least one sublocationnested in one or more higher locations as exemplified in FIG. 1, a userstatus information may be synchronized by obtaining and comparing theuser status information from the sublocations and the user statusinformation from the higher location in order to determine the user'sstatus in such nested location. For example, when a user checks out of asublocation, it still remains in checked in status on the associatedhigher location. If the user is in checked in status on a sublocationand then checks out of a high location, the user will be assumed aschecked out on all sublocations nested by the higher locationautomatically. Furthermore, when a location includes multiple checkpointmonitors, the user status information may be synchronized automaticallyas soon as the status is updated in one of the checkpoint monitors.

FIG. 2A shows the checkpoint monitor 102 including a head section 112Aand a body section 112B in its installed state in a monitored location.FIG. 2B shows, in top view, the head section 112A may be cylindrical andmay comprise a plurality of cameras 114 and a plurality of presencesensors 116 for having 360 degrees image capture and sensing capability.The presence sensors 116 may sense any intrusion, presence or entry,such as an entry of an object, person or both, into the checkpoint zoneZ. The presence sensors 116 and the cameras 114 may be integrated towork in a synchronized manner to sense and image 360 degrees. Thepresence sensors 116 and the cameras 114 may also operate individuallyto determine a user's direction of access, i.e., entry and exitdirection, in the checkpoint zone Z, i.e., to determine user's directionof entry into and exit out of a checkpoint zone. In this respect, thecheckpoint zones Z may be defined by the range of the presence sensor116 around the checkpoint monitors 102. An exemplary checkpoint zone Zmay be in the range of 1-100 meters, preferably 2-10 meters in diameter.A display 118 on the head section 112A may display various statusrelated information in use. Warning and guide lights 117 may give usersvisual warnings for valid and invalid operations using different colorlight, such as red for invalid operations and green for validoperations. The warning and guide lights may also be configured asarrows to point at in and out directions of the monitored location toguide users. The body section 112B may contain critical inner componentsof the checkpoint monitors 102, such as a server having a processor, adata storage and a control software with various modules, powerconnections and/or power supply, various communication, data capture anddetection hardware and the like devices.

FIG. 3 shows an exemplary embodiment of the monitoring system 100integrating the system server 103 with a plurality of checkpointmonitors (CM) 102 installed in each monitored location and clientinterfaces 104 of each client organization associated with the monitoredlocations. In this embodiment, an independent monitoring organizationmay own the system server 103 and the checkpoint monitors 102, andoperate the compliance monitoring process for the client organizationsin the client organizations' locations. Alternatively, the system 100including the system server 103 and the checkpoint monitors 102 may beowned by an organization having locations to be compliance monitored.

The checkpoint monitors 102 may be in communication with the systemserver 103 via a first communication network 120A or a first network,which may be a wireless or wired communication channel, or both. Theclient interfaces 104 may be in communication with the system server 103via a second communication network 120B or second network, which mayalso be a wireless or wired communication channel, or both. Accordingly,the monitoring system 100 may manage a multiplicity of locations havingat least one checkpoint monitor 102 and for a multiplicity oforganizations related to such locations. For example, a first group(Group-A) of checkpoint monitors 102 may be installed in a firstlocation to compliance monitor for a first client 104A; a second group(Group-B) of checkpoint monitors 102 may be installed in a secondlocation to compliance monitor for a second client 104B; a third group(Group-C) of checkpoint monitors 102 may be installed in a thirdlocation to compliance monitor for a third client 104C; and a fourthgroup (Group-D) of checkpoint monitors 102 may be installed in a fourthlocation to compliance monitor for a fourth client 104D, and so on.

FIG. 4 is a block diagram illustrating components of checkpoint monitor102 including a checkpoint server 130, or a local server, with a datastorage 132, or database storing a control program 138 or software, aprocessor 134, and a communication module 136. The checkpoint monitormay also include a plurality of modules 140 that may be connected to theprocessor 134 while their corresponding software modules may be storedin the checkpoint server 130. An access module 140A, or areceiver/decoder module, receives an access code signal 141, includingan access code, from an access code device 142 operated by a useraccessing the checkpoint zone Z of the checkpoint monitor 102. Thecheckpoint monitor 102 may be powered by a power supply unit 131 whichmay be connected to a solar panel or power network to receive power.

The access code device 142 may be a wireless device or wired device thatis part of the checkpoint monitor 102, and may be designed as a mobiledevice operable by the user. The access code in the access code signal141 may comprise a user identification (ID) code component and a useractivity code component. The user ID code may be a unique number orbarcode associated with the user and may be used to identify both theaccess code device 142 and the user who is authorized to carry andoperate it. The user activity code may identify an activity status ofthe user, and which may be real time selected by the user when theaccess code device 142 is operated within or adjacent the checkpointzone Z.

There may be a plurality of user activity codes which may be used todefine various user activities to track the user compliance whileattending the scheduled assignments in the location 101 (FIG. 1). In oneembodiment, the user may select the activity code by operating activitybuttons of the access code device 142 by pressing on them. Operatingactivity buttons of the access code device 142 may also transmit theaccess code signal 141 including both the user identification code andthe selected user activity code. Each activity button on the access codedevice 142 may have assigned activity indicators. In this embodiment,for example, selecting the button with “in” indicator may add “check in”activity code to the access code signal indicating that the user isentering the monitored location; and selecting the button with “out”indicator may add “check out” activity code to the access code signalindicating that the user is exiting the monitored location. Although inthis example the access code device 142 includes two activity buttons,it may have multiple buttons, each assigned to one or more user activitycodes. Further, the buttons used in this embodiment may be replaced withany pressure or touch activated surfaces, zones or devices such as keys,keypads, touchpads or touchscreens. As will be more fully describedbelow, the user ID code and the user activity code may be used todetermine user's assignment status and activity status by the checkpointmonitors 102 in the monitored location.

In alternative embodiments, the access code device 142 may have moreactivity buttons or zones with assigned activity indicators. Exemplaryadditional activities may be related to the reporting progress on apre-assigned specific task in the monitored location by utilizingactivity buttons indicating activities, such as “complete”, “canceled”,or “continue”, etc. Other exemplary activity buttons or zones may be forreporting damage in the equipment, security or safety related aspects,and the like. In another embodiment, a mobile phone may be used as anaccess device using a suitable mobile phone application allowing anaccess code signal to be sent to the checkpoint monitor via the mobilephone network. A keypad or touchscreen of the mobile phone may be usedto select a wide variety of activity indicators utilizing eitherpre-assigned keys or by simply typing in to add activity codes to theaccess code signal which also carries user ID or the user ID code. Asdescribed above, each activity code may indicate a unique user activitystatus. The access code signal 141 may be received and decoded by theaccess module 140A, and the decoded user ID code and activity code maybe stored in the data storage 132 and also shown on the display 118 onthe checkpoint monitor 102.

A sensor module 140B may be used for peripheral presence detection usingfor example infrared radiation, sonar, laser or audio detection sources.The sensor module 140B may be integrated to and operate the sensors 116(FIGS. 2A-2B). An image module 140C may be used for peripheral imaging,activity tracking and recognition purposes, and may use video, stillimaging (photos) and infrared imaging. The image module 140C may beintegrated to and operate the cameras 114 (FIGS. 2A-2B). The imagemodule 140C may be configured to take one or more pictures, including auser picture, once an intrusion into the checkpoint zone Z is sensed bysensor module 140B. A user access and routing module 140D may be usedfor automated access and routing to, for example, control automatedgates if there is any. An integration module 140E may provide dataintegration between the modules 140A-140D and their correspondinghardware and other required networking. The communication module 136 maybe a transceiver module to establish wireless communication between thecheckpoint monitors 102 and the system server 103 via the communicationnetwork 120A.

An exemplary access module 140A for user identification may include oneor a combination of the following technologies: generic 300 to 900 MHztransmitters and receivers, RFID technology (e.g., HID tags and badgereaders), biometric reading devices, proprietary software authenticationvia proximity user cell phone connectivity using Bluetooth or WiFi atcheckpoint, face recognition software, license plate detection software(e.g., locally installed software or Google cloud vision API, IBM Watsonvisual recognition, Open ALPR Cloud API, IBM i2 iBase Plate Analysis,etc, or T2 systems ANPR). An exemplary sensor module 140B for presencedetection may include one or a combination of the followingtechnologies: motion detectors with single or combined technologies, forexample, passive infrared sensors (e.g., Panasonic AMN), passiveinfrared array sensors (e.g., Panasonic Grid Eye), software analyticsfor motion detection on camera images (standard visible light/IR camerasand thermal imaging cameras e.g. FLIR Lepton), light Detection andRanging Sensors a.k.a. LiDAR which is a Laser based technology (e.g.,Leddar IS16, Quanergy M8 or S3), ultrasonic motion detectors, andmicrowave motion detectors, and the like. An exemplary image module 140Cfor visual identification or imaging may include one or a combination ofthe following technologies: visible light and infrared combinationcameras (e.g. ELP 720P, FLIR PE133E) and thermal Imaging Cameras (e.g.,FLIR TCX). For communications between the checkpoint monitors 102 andthe system server 103, an internet based network may be used and toaccess the internet on remote locations either a cellular modem (e.g.,Multitech MTR-LAT1) or a satellite modem (e.g., Newtec MDM2200 IPSatellite Modem) may be used.

The data storage 132 stores various files including data that supportsmany functions of the checkpoint monitors 102. The data storage 132 maystore data files including, but not limited to, an assignment data file133 including a data related to user assignment status information andvarious predetermined user status information, a user data file 137including user pictures and assigned ID codes; checkpoint monitor (CM)data file 139 including data related to the checkpoint monitor'sassigned ID and GPS coordinates, location map; a system data file 143including data related to the configuration of the checkpoint monitor,activity logs, system logs, activity media recordings (pictures, videosetc.). As also exemplified in FIGS. 6-7B, the assignment data file 133stored in the data storage 132 may comprise at least one assignment datatable 135 including assignment status data 160A and activity status data160B of a plurality of authorized users assigned for work in thatparticular location where the checkpoint monitors storing the assignmentfile are located. The assignment status data 160A may be a listindicating each user's assignment status with user's identification,such as user name; company name; location identification, and thespecific date and time that indicate each user is scheduled for work.For example, A. Smith; Alpha, Inc.; Houston-TX-USA, Field-A1 Jan. 9,2017; 08:00 AM-10:00 AM. As described above, in one embodiment, theuser's identification may be associated with the access code device andthe user ID code transmitted from the access code device assigned to theuser, which is received by the checkpoint monitor and, after decoded,compared against the users on the assignment data table 135 stored inthe data storage 132. In this example, this company authorized employeeis expected to be checked in this particular location at 08:00 AM andchecked out at 10 AM.

Activity status data 160B of the users may also be kept on theassignment data table 135 and next to the assignment status data 160A.In this configuration, the assignment data table includes each user'scurrent activity and assignment status. As described above, the useractivity code indicating the user activity status may be transmittedwithin the access code signal 141 along with the user ID code. However,differing from the user ID code which may also be the identification ofthe access code device of the user, the user activity code may beselected and transmitted by the user on the location using the readilyavailable selectable functions of the access code device 142 (FIG. 4).In the above example, when the user selects “in” option as he isentering the monitored location, his activity status on the assignmentdata table 135 is updated as “in” with check in timestamp. Similarly,when the user selects “out” option as he is leaving the monitoredlocation, his activity status on the assignment data table is updated as“out” with check out time stamp. The assignment data table 135 may alsoinclude IDs of all the checkpoint monitors, such as a unique numberassigned to them, in the monitored location. The assignment data table135 contains the most recent activity status update conducted by a userat any checkpoint monitor 102 at the monitored location or an activitystatus update enforced by the system server 103. This most currentactivity status may be referred to as static status or the currentstatus. The system data storage 132 may be in the form of non-transitorycomputer readable medium configured to store files, programs, tables andexecutable computer instructions. A computer program product stored on anon-transitory computer readable medium may include instructionsexecutable by the processor or controller of the server to operate thecheckpoint monitor 102.

FIG. 5 is a block diagram illustrating the monitoring center server 103,or the system server, with a data storage 150 or system database, aprocessor 152, an operational interface 154A, an administrativeinterface 154B, a first communication module 156A and a secondcommunication module 156B, a system control program 158 or software andvarious program modules stored in the data storage 150. The system mayalso have multiple levels of access with different features available oneach level. Within the context of this invention, users in differentprofessional classes may belong to an internal group or external group.An internal group may comprise technical administrators, operationsmanagement, and technicians. External groups may comprise clientadministrators, and operators or employers (referred to as “users” inthis application). Depending on the group and level, different filtersmay be applied to the data presented. For instance, an external groupuser may not be able to see engineering or technical details on the datapresented to them as it would be to a user in an internal group. Anexternal operator should be able to see the data pertaining only to hisactivity, not the engineering data. An external client administrator maysee the activity pertaining to his/her locations and users, but not theothers or the engineering data. An internal operations manager may seelocations and user activity for all the existing and past clients, andso on.

The monitoring system 100 may be managed by the system server 103 usingthe programs and data stored in the data storage 150. The data storage150 stores various program files including data that support manyoperations of the monitoring system 100.

The first communication module 156A may communicate with checkpointmonitors 102 in the monitored location. The first communication module156A may apply network data encryption and decryption to the data sentand/or received from the checkpoint monitors 102. The firstcommunication module 156A may transport data securely and reliablyrelated to the transactions between the control program 158 of systemserver 103 and the control software 138 of the checkpoint monitors 102.The second communication module 156B may communicate with the clientorganizations via client interfaces 104. The second communication module156B may apply network data encryption and decryption to the data sentand/or received from the checkpoint monitors 102. The secondcommunication module 156B may register time of various data receivedfrom the client interfaces 104 and processes commands and responses toand from the client interfaces 104.

The control program 158 of the system server 103 may include manyutility program modules for implementing various features used in thesystem 100. Exemplary utility program modules may be as follows: acheckpoint monitor set up and test program module for introducingcheckpoint monitors to the system 100 by adding, detecting and testingcheckpoint monitors 102 as well as assigning locations and IDs for them;a data control program module to retrieve and store data in the datastorage 150; and an interface program module to provide and control thecommunication interfaces. The operational interface 154A allowsmonitoring center staff to track the real time operation of themonitoring system 100 and assist the operation by providing commands andneeded information based on the observations. The administrationinterface 154B may handle administrative aspects of the monitoringsystem 100, such as, but not limited to, system configurations,management schedules, client related operations, user activity statusinformation and the configuration of monitoring checkpoints. Optionally,there may be an automatic pre verification and validation operation inplace before handling such administrative aspects.

The data storage 150 may store data files used in the operation of thecompliance monitoring process using the data received from thecheckpoint monitors; data files received from and sent to the clientorganizations; and data files used in operating the monitoring system.The data files stored in the data storage 150 may include, but notlimited to, assignment data files 153 including assignment data relatedto user assignment status information and various predetermined userstatus information of each client organization; checkpoint monitor datafile including each checkpoint monitors assigned ID and GPS coordinates,location identifiers and location maps; a user data file including userpictures, assigned ID codes and their organizations; a client data fileincluding services requested by each client organization and relatedinformation; a system data file including data related to theconfiguration of the system server 103. The system data storage 150 maybe in the form of non-transitory computer readable medium configured tostore files, programs, tables and executable computer instructions. Acomputer program product stored on a non-transitory computer readablemedium may include instructions executable by the processor orcontroller of the server to operate the system 100.

As also shown in FIGS. 6-7B, the assignment data files 153 stored in thedata storage 150 may comprise the assignment data tables 135 includingassignment status data 160A of a plurality of authorized users assignedfor work in a particular location of each organization acquiringcompliance monitoring. As will be described more fully below, theassignment data tables 135 in the data storage 150 may be updated withthe activity status data 160B received from at least one of thecheckpoint monitors 102 in the monitored location and the updatedassignment data table 135 in the data storage 150 replace the assignmentdata tables in the data storages 132 of all the check point monitors 102installed in the monitored location. In this respect, the data storage150 may have a plurality of assignment data files 153, such as 153A,153B, 153C, 153D and so on, each belonging to a client organizationacquiring compliance monitoring services from the monitoringorganization (See FIG. 3). Each client organization may, in turn, have aplurality of assignment data tables 135, such as 135A, 135B, 135C, 135Dand so on, each related to a corresponding monitored location. It isunderstood that, depending on the task in the monitored location, theremay be more than one assignment data table may be used so that differenttask performed in for example sublocations shown in FIG. 1 may bemonitored by the client organizations.

The monitoring center infrastructure may be hosted on a monitoringcompany managed location. Server computing hardware may be a single or amultitude of tower or rack servers (e.g., Dell PowerEdge Servers). Suchservers may be provided with a multitude of communication networksconfigured with a combination of networking routers (e.g., Cisco 4351ISR) and or switches (e.g., Cisco Catalyst 3650 Series) protected bysecurity devices (e.g., Cisco ASA 5500-X Series Next-GenerationFirewall). A cloud based infrastructure may be for example the AmazonWeb Services or Microsoft Cloud where the system may be hosted on theirphysical systems with greater flexibility for implementation and growth.Custom software developed on many alternative environments may beinstalled on any of the systems mentioned above. Databaseimplementations like SQL server or Oracle may be utilized as well.

FIG. 6 illustrates an exemplary assignment data table 135A includingassignment status data 160A and activity status data 160B for the usersauthorized to work in the same monitored location. As also describedabove, the assignment status data 160A may include identifications ofthe users, their company, the region where the monitored location islocated, location identification, dates and specific hours that theyhave scheduled work assignments, identification of the checkpointmonitors located in the location, for example, checkpoint monitors (CM)with numbers 1, 2, 3, 4 and 5. The assignment status data may alsoinclude user driver license information and/or an image copy of thedriver license. The activity status data 160B may include the lastupdated activity status of the users of the location. Accordingly, inFIG. 6, the activity status data 160B shows that the two of the userscompleted their tasks in the location earlier in the week and they are“out”, and the last user is still in the location and “in” at accordingto the latest update. However, as mentioned above, the activity statusdata may include other activity or operational updates informing orreporting other operational activities from the monitored location viathe user accessing the location.

FIGS. 7A and 7B illustrate both the data storage 150 of the systemserver 103 and the data storage 132 of the checkpoint monitors 102storing the same assignment data table 135A of the client organization.If any of the users' activity status in the monitored location isupdated by one of the 5 checkpoint monitors 102, the assignment datatable 135A at the system server 103 is updated and the updatedassignment data table version instantly replaces the old versions in allcheckpoint monitors in the monitored location. Furthermore, when newassignment data tables are received through the client interface of thesystem 100, the assignments tables in all the checkpoint monitors 102 inthe monitored location are replaced with the new assignment data tables.

In the data storage 150, the assignment data table 135A may be kept inthe assignment data file 153A of the client organization, which may holdmany assignment data tables 135 for the same organization and for themonitored location as well as a multiplicity of other similarlymonitored locations. The data storage 150 may hold a plurality ofassignment data files 153 for a plurality of client organizations,wherein each assignment data file may hold a plurality of assignmentdata tables 135. Alternatively, the data storage 150 may store a singledata table or data file including all the assignment status data andactivity status data for all the client organizations as well as all theother data used to operate the monitoring system 100 for monitoring thelocations of the client organizations. The system program 158 isconfigured to manage such single data table including all the data ordata distributed into a plurality of data files or data tables, andthese aspects are within the context of this invention.

FIG. 8 is a flowchart 200 illustrating an exemplary operation sequencein the system 100 of the present invention. Referring to FIGS. 8 and1-7B, accordingly, in step 202, client data may be received from theclient organization via the client interface 104 and stored in the datastorage 150 of the system server 103. The client data file may include adigital map of the field, a user assignment file including user IDs andpictures as well as an assignment schedules. An assignment data table135 including users' assignment status data and their activity statusdata may be created in the system server 103 and stored in the datastorage 150.

In step 204, each user may be assigned to an access code device 142 withan access code identifying the user. The user's assigned access code maybe linked to the user ID in the assignment data table 135. Thisoperation links the user and the access code device to the assignmentlocation identified on the assignment data table.

In step 206, each checkpoint monitor 102 may be assigned an ID andassociated with the monitored location by either linking the assignedcheckpoint monitor IDs to the location identified in the assignment datatable 135 or directly linking them to the location at the system server103. Similar to the user assignment to the field, the checkpointmonitor's setup process may be based on linking the checkpoint monitors102 to the location of use. Resources that may be added or removed fromthe selected location may be users and checkpoint monitors. A checkpointmonitor may be deployed and added to a particular location stored on thesystem server 103.

Although it is part of the initial setup, the checkpoint monitorsreceives periodic updates of the assignment data table 135 that includesthe approved users established on the location and the latest activitystatus based on the latest synchronization for thatlocation/sublocation. Once the users and the checkpoint monitors 102 arelinked the monitored location, the assignment data table 135 may bedownloaded from the data storage 150 of the system server 103 to thedata storage 132 of the checkpoint monitors 102. Alternatively, asmentioned above, the data storage 150 may store a single data table ordata file including all the assignment status data and activity statusdata for all the client organizations. In this case of having the singledata table, desired data is downloaded to the checkpoint monitor. Next,the user activity status may be updated to its initial setting aschecked out to make the checkpoint monitors ready for monitoring in thelocation. This step completes the in-office set up process of thecheckpoint monitors. In step 208, the checkpoint monitors 102 may beplaced into their shipping containers, transported to the location andinstalled therein. In step 210, once installed in the field, thecheckpoint monitors 102 are powered and wirelessly connected to thesystem server 103.

FIG. 9 is a flowchart 300 illustrating, in one embodiment, a compliancemonitoring algorithm that monitors access to the location to bemonitored using the checkpoint monitors 102 installed in the location inconnection with the system server 103. Each checkpoint monitor 102 maybe configured to authenticate both the assignment status and theactivity status of the user by analyzing the access code that istransmitted to the checkpoint monitor 102 from a user access codedevice. Referring to FIGS. 9 and 1-7B, accordingly, in step 302, when anintrusion or activity in the checkpoint zone Z is detected, thecheckpoint monitor 102 is placed in a standby mode for a predeterminedtime to receive an access code signal 141 from the access code device142. In step 304, if no access code is received during the standby mode,the checkpoint monitor reports the event as an invalid operation in step305 to the system server 103 of the monitoring center. The reportedinvalid operation in step 305 may be recorded as unauthorized entrywhich may be on the basis of a timeout or incomplete process. However,the invalid operation in step 305 may also occur when an entry intoand/or exit out of the checkpoint zone detected by the sensors withoutreceiving an access code. If an access code from the access code deviceis received in step 304, in step 306, the checkpoint monitor beginsauthenticating the assignment status of the user that transmitted theaccess code.

The assignment status of the user may be authenticated by comparing anID code component of the access code against the user ID codes in theassignment data table stored in the data storage 132 of the checkpointmonitor 102 to determine whether the user is assigned for a scheduledwork in the field. In step 308, if the assignment status of the user isnot approved, i.e., the user is not assigned for a scheduled work in thefield, although the user is an identifiable user with an access codedevice, the checkpoint monitor reports the event as an invalid operationin step 309 to the system server 103 of the monitoring center with theuser ID involved. However, the invalid operation reported in step 309may be still recorded as a valid event but with a lower score indicatingthat it is triggered by an authorized user, which may require aninvestigation by the client. As is understood, the system may include aplurality of such scoring levels indication specific combination ofevents done by the authorized users and unauthorized users.

If the assignment status of the user is approved in step 308, i.e., theuser is assigned for a scheduled work in the field, in step 310, thecheckpoint monitor begins authenticating the activity status of the userwhose assignment status has been approved. The activity status of theuser may be authenticated by authenticating the activity code or theactivity status indicator added to the access code signal by the user toprovide that the user is either in a check in activity to access themonitored location or in a check out activity to exit the monitoredlocation.

In step 312, if it is determined that the user activity status is notcheck in, i.e., the user is selected “out” option when transmitting theaccess code signal, in step 313, the activity status of the user in theassignment data table, which is stored in the checkpoint monitor, may beupdated as check out. Further, in step 314, the checkpoint monitorreports the updated check out status as a valid operation to the systemserver 103 of the monitoring center with the associated user ID. In step312, if it is determined that the user activity status is check in,i.e., the user is selected “in” option when transmitting the access codesignal, in step 315, the activity status of the user in the assignmentdata table may be updated as check in. Further, in step 316, thecheckpoint monitor reports the updated check in status as a validoperation to the system server 103 of the monitoring center with theassociated user ID. Furthermore, a scoring system may be used as aqualifier of a check-in or check-out operation based on the traveltrajectory followed by a user as detected by the checkpoint monitor 102.The objective is to validate that the user enters the location premisesif a valid check in is detected and that the user leaves the location ifa valid check out is detected.

Once the system server 103 receives the transmitted activity status ofthe user with or without authenticated assignment status, the assignmentdata table 135A in the data storage 150 may be updated with the newactivity status data of the user. In the following step, the updatedassignment data table or data is transmitted to the rest of thecheckpoint monitors in the monitored location to update the assignmentdata tables stored in each checkpoint monitor. In the next step, thesystem server 103 may provide the updated activity status of the user tothe related client organization in a report via the client interface.Each checkpoint monitor 102 may also be configured to operateindependently if they cannot communicate with the system server 103 forsome technical reason or communication problem. In such cases, thecheckpoint monitors may store both an assignment status data and anactivity status data of the user after analyzing the access code signaltransmitted to the checkpoint monitor. The stored data may betransmitted to the system server once the communication isreestablished.

FIG. 10 is a flowchart 400 illustrating an exemplary embodiment ofassigning both the checkpoint monitors and the users to a selectedlocation prior to initiating the compliance monitoring of the presentinvention in the location of the client organization. In the flow chart400, for clarity, exemplary operation steps which may be conducted usingthe system server 103 at the monitoring center of the monitoringorganization may be shown within the box 400A and exemplary operationsteps which may be conducted at the location using the checkpointmonitors 102 may be shown within the box 400B.

Referring to FIGS. 10 and 1-7B, accordingly, in operation step 402A,initially, the number of checkpoint monitors 102 and their installationpositions in the assigned location are determined by either a clientorganization admin (client admin) via a client interface 104 (FIG. 3) ora monitoring organization admin (monitoring admin). However, themonitoring organization admin may be the only authority to allocatecheckpoints and perform assignments based on prior agreement with clientadmin. Once the setup is completed, in operation step 404A, themonitoring admin may assign the checkpoint monitors to the location bylinking their identifications, such as identification numbers, to thelocation. In one embodiment, the check point monitor assignment may bedone by placing the identification numbers of the checkpoint monitors102 on the assignment data table, as exemplified in FIG. 6. Next, inoperation step 402B, checkpoint monitors may be taken to the assignedlocation and installed at the predetermined positions in the location(see FIG. 1), tested and deployed. In operation step 406A, the clientadmin may request to add new users to the assignment data table for thesame location, and in operation step 408A, the monitoring admin mayupdate the assignment status of users in the assignment data table bylinking them to the assigned location (FIG. 6).

In one embodiment, the linking of users to the assigned location may bedone by placing user identification and/or user ID code of the useraccess code device to the assignment data table. In operation step 410A,the client admin may request to remove one or more users from theassignment data table of the location, and in operation step 412A, themonitoring admin may update the assignment status of the users in theassignment data table by removing the users requested to be removed. Inoperation step 414A, the client admin may request to change useractivity status of one or more users on the assignment data table of thelocation, and in operation step 416A, the monitoring admin may updatethe activity status of the users in the assignment data table bychanging their activity status into the activity status requested by theclient admin. In operation step 418A, the data, including the assignmentdata table, from the operation steps 402A-416A may be processed andfiltered, and in operation step 420A, the data including the assignmentdata table may be stored in the storage 150 of the system server 103(FIG. 5).

In operation step 406B, an updated and approved assignment data tablemay be received at the checkpoint monitors at the location after theoperation step 418A, and upon request from the check point monitors inoperation step 404B. In operation step 408B, feedback from thecheckpoint monitors such as activity status updates, valid and invalidoperations etc., may also be processed in operation step 418A and storedin the data storage 150.

FIGS. 11A-11D show various flowcharts illustrating various embodimentsof methods using the monitoring system 100 including valid and invalidoperation examples. FIG. 11A shows a flowchart 500A exemplifying anembodiment of a valid operation sequence involving authentication of theassignment status and activity status of an authorized user. Referringto FIGS. 11A and 1-7B, accordingly, in operation step 502A a user mayaccess the checkpoint zone Z (see FIGS. 1 and 2A) of checkpoint monitor102 in the location. In operation step 504A, the checkpoint monitor 102may sense the user accessing the checkpoint zone and providesaudiovisual feedback as well as prompts for user access code. The usermay provide the access code signal within a predetermined response time,for example, 10-30 seconds. During the response time a video or stillimage of the user may be recorded by the checkpoint monitor 102 as imagedata and stored. In operation step 506A, the user may activate the useraccess code using the access code device assigned to the user. Inoperation step 508A, the checkpoint monitor may receive the access codesignal, decode it and authenticate user's assignment status as validassignment by comparing the user ID code component of the access codesignal against the user identifications in the assignment data table135, and register and report it as valid operation.

In operation step 510A, the checkpoint monitor may authenticate the useractivity code component of the access code signal to determine theactivity status of the user. If the determined activity status isopposite to the current activity status on the assignment data table,the user activity status on the assignment data table is updated asdescribed above via the system server 103. The checkpoint monitor 102may register and report the updated activity status as valid operation.In operation step 512A, the checkpoint monitor may provide anaudiovisual approval feedback to the user and prompt to proceed. Inoperation step 514A, the user may depart the checkpoint zone in thedirection of either into the monitored location or out of the monitoredlocation. In operation step 516A, once the checkpoint monitor 102 sensesuser's departure, a qualitative score may be calculated based on thevalid operations. In operation step 510A, data obtained from theoperations steps 502A through 516A may be transmitted to and received bythe system server 103. As described above, the system server 103 mayform and transmit an updated assignment data table to the checkpointmonitor(s) 102.

FIG. 11B shows a flowchart 500B exemplifying an embodiment of an invalidoperation sequence involving an unauthorized access attempt. Referringto FIGS. 11B and 1-7B, accordingly, in operation step 502B, an access orintrusion to the checkpoint zone Z (see FIGS. 1 and 2A) of checkpointmonitor may occur. In operation step 504B, the checkpoint monitor maysense the intrusion triggered by a person or object and provideaudiovisual feedback as well as prompts for user access code and startsthe response time. During this time a video or still image of thecheckpoint zone Z may be recorded by the checkpoint monitor 102 as imagedata and stored. In operation step 506B, no access code signal may bereceived within the response time by the checkpoint monitor 102 or theaccessing person or object may no longer be sensed within the checkpointzone Z. In operation step 508B, the checkpoint monitor may detect adeparture from checkpoint zone Z and report the event as an invalidoperation, and in operation step 510B, the main server receives andstores the invalid operation. In operations steps 504B and 508B, thedetections may be sequential detections triggering unauthorized entryand/or exit.

FIG. 11C shows a flowchart 500C exemplifying an embodiment of an invalidoperation involving an invalid access status of a user. Referring toFIGS. 11C and 1-7B, accordingly, in operation step 502C a user mayaccess the checkpoint zone Z (see FIGS. 1 and 2A) of checkpoint monitorin the location. In operation step 504C, the checkpoint monitor maysense the user accessing the checkpoint zone and provides audiovisualfeedback as well as prompts for user access code. The user may providethe access code signal within a predetermined response time, forexample, 10-30 seconds. During the response time a video or still imageof the user may be recorded by the checkpoint monitor as image data andstored. In operation step 506C, the user may activate the user accesscode signal using the access code device assigned to the user. Inoperation step 508C, the checkpoint monitor may receive the access codesignal, decode it and authenticate user's assignment status as validassignment by comparing the user ID code component of the access codesignal against the user identifications in the assignment data table135, and register and report it as valid operation.

In operation step 510C, the checkpoint monitor may attempt toauthenticate the user activity code component of the access code todetermine the activity status of the user. If the determined activitystatus is the same as the current activity status (unchanged) on theassignment data table or the user activity code command is notrecognizable, the user activity status on the assignment data table maynot be updated. The checkpoint monitor 102 may register and report theactivity status as invalid operation. In operation step 512C, thecheckpoint monitor may provide an audiovisual disapproval feedback tothe user and prompt to retry. If the user retries to authenticateactivity status from operation step 506C and succeeds, the operationsequence continues as in FIG. 11A with a valid operation. If not, inoperation step 514C, the user may depart the checkpoint zone in thedirection of either into the monitored location or out of the monitoredlocation. In operation step 516C, once the checkpoint monitor 102 sensesuser's departure, a qualitative score may be calculated based on theinvalid operation. In operation step 510C, data obtained from theoperations steps 502C through 516C may be transmitted to and received bythe system server. As described above, the system server 103 may formand transmit an updated assignment data table to the checkpointmonitor(s).

FIG. 11D shows a flowchart 500D exemplifying an embodiment of an invalidoperation involving an invalid assignment status of a user. Referring toFIGS. 11D and 1-7B, accordingly, in operation step 502D a user mayaccess the checkpoint zone Z (see FIGS. 1 and 2A) of checkpoint monitorin the location. In operation step 504D, the checkpoint monitor maysense the user accessing the checkpoint zone and provides audiovisualfeedback as well as prompts for user access code. The user may providethe access code signal within a predetermined response time, forexample, 10-30 seconds. During the response time a video or still imageof the user may be recorded by the checkpoint monitor as image data andstored. In operation step 506D, the user may activate the user accesscode using the access code device assigned to the user. In operationstep 508D, the checkpoint monitor may receive the access code signal,decode it and attempts to authenticate user's assignment status bycomparing the user ID code component of the access code signal againstthe user identifications in the assignment data table 135 in thecheckpoint monitor 102. If the determined assignment status cannot bedetermined, i.e., the user is not on the assignment data table or notscheduled for the specific check-in time, the checkpoint monitor mayregister and report the assignment status as an invalid operation.

In operation step 512D, the checkpoint monitor may provide anaudiovisual disapproval feedback to the user and prompt to retry orcontact the administration. If the user retries to authenticateassignment status from operation step 506D and succeeds, the operationsequence continues as in FIG. 11A with a valid operation. If not, inoperation step 514D, the user may depart the checkpoint zone in thedirection of either into the monitored location or out of the monitoredlocation. In operation step 516D, once the checkpoint monitor sensesuser's departure, a qualitative score may be calculated based on theinvalid operation. In operation step 510D, data obtained from theoperations steps 502D through 516D may be transmitted to and received bythe main server. As described above, the system server may form andtransmit an updated assignment data table to the checkpoint monitor(s).

Another embodiment of the compliance monitoring system of the presentinvention will be described below with FIG. 12A through FIG. 18.

Hydrocarbon wellsites may experience a large volume of vehicles, such astrucks and personnel vehicles, entering and exiting the wellsites on adaily basis in addition to the personnel having work assignments in thewellsites. Owners of the hydrocarbon wellsites may wish to carefullymonitor all vehicle entry and exit from the hydrocarbon wellsites tocheck and collect information related to the vehicles along with theassociated personnel in an effective manner.

To address this need, in another embodiment, the system of the presentinvention may further provide portable access control stations that maybe electronically integrated to the networked checkpoint monitorsdescribed in the previous embodiment. A portable access control stationmay automatically grant entry and exit to a users, such as vehicledriver and/or at least one of the vehicle occupants, as well as thevehicle associated with such users when a preauthorized access code,which is associated with the user and identifying him/her, is deliveredelectronically to the portable access control station.

As illustrated in FIGS. 12A-12B, in this embodiment of the presentinvention, a compliance monitoring system 600 may include a systemserver 603 at a monitoring center and one or more access controlstations 700 or access control assemblies 700, which are remotelylocated in a monitored location 601 or the monitored location having aperimeter 605. Each access control station 700 may include a check pointmonitor 602A and an access control unit 702 that is electronicallyintegrated with the checkpoint monitor 602A. The access control unit 702may be configured to operate an alert member to alert the drivers to thepresence of the access control station where the check in or check outprocesses are performed. Alternatively, the compliance monitoring system600 may also optionally include one or more individual checkpointmonitors 602B located on the same monitored location. The system server603 is in wired or wireless connection with the access control stations700, and the individual checkpoint monitors 602B.

The monitored location 601 may be a wellsite, oilfield, hydrocarbonfield, or a hydrocarbon location, for oil or natural gas production orrecovery, where the users of it may be compliance monitored by thesystem 600. The monitored location may be a remote location. As will bedescribed more fully below, the access control stations 700 may beportable stations and, thus easily deployable and installable inselected locations of the monitored location 601. Furthermore, theaccess control stations 700 and optionally the individual checkpointmonitors 602B may also be located in or adjacent various work locations608, such as work locations 608A and 608B nested within the monitoredlocation 601. This way, further compliance monitoring of the users ofsuch work locations may be performed. Access control stations 700 aresubsystems of the system 600. Built-in instrumentation and enhancedcontrols of the access control stations 700 may enable a safer and quickoperation. The equipment is designed to expedite and facilitate therelocation of the networked compliance monitoring system with thefrequency demanded by oilfield operations and with a minimal footprintwhere location space is highly constrained. The access control unit 702of the access control station may receive commands from both thecheckpoint monitor 602A and the manual controls such as a numerickeypad, wireless remote or an emergency stop.

As shown in FIG. 13, the checkpoint monitor 602A and the access controlunit 702 of the access control station 700 may be electronically andmechanically integrated and installed adjacent to one another at anaccess location 606 of the monitored location which may be on an accessroad, pathway or roadway used by the vehicles. In one embodiment, at theaccess location 606, the access control station 700 may monitor avehicle by both monitoring vehicle events and events of the users (userevents) associated to the vehicle. Vehicle events may be monitored bythe access control unit 702 and the user events may be monitored by thecheckpoint monitor 602A of the access control station 700. The usersassociated to a vehicle may be, for example, vehicle driver and/or anoccupant of the vehicle, and their previously registered assignment datain the system server indicates that they will either use or drive thevehicle, i.e., they are associated with the vehicle.

The access control station 700 may collect and store vehicle event datacombined with user event data, which is associated to the vehicle eventdata, and transmit both data to system server to monitor vehicleactivity. Vehicle event data may be the vehicle data captured by theaccess control unit 702, which may be vehicle detection, vehicle arrivalat the access location and departure from the access location, foreither exiting or entering the monitored location 601, and other eventdata captured by the access control unit 702. Associated user event datamay be user's assignment status identifying the user and his/herassignment in the monitored location 601 and user's activity indicatingwhether the user is entering the monitored field or exiting. With thiscombined data, the system may make a determination about the vehicle asto what time it is entered or exited to location and for what workassignment. If the system receives only a user event data without anyvehicle event data, the system may make determination only for user'sstatus.

User's assignment status data about the assigned work and activitystatus data about user's entry to and exit from the monitored location601 may be monitored and registered by the checkpoint monitor 602A ofthe access control station 700. User assignment data and activity dataare transmitted from the checkpoint monitor server 634 of the checkpointmonitor 602A to the system server 603 and stored thereon (See FIG. 16).The data collected by monitoring the user and the vehicle at the accesscontrol station 700 may be observed and tracked by administrators at themonitoring center in real time as such activity occurred. The accesscontrol station's messages may carry distinct IDs and/or distinctdescriptions that facilitate filtering and processing when delivered tosystem administrators and any other personnel who may be in charge ofmonitoring the particular hydrocarbon field where the access controlstation 700 is installed.

In one embodiment, data related to user events such as assignment statusand activity status of the users may be the only data stored on theserver 603. Access control unit 702 related events may also be storedalong with the user events at the system server 603. The sequence andtime correlation of the user events and the access control unit relatedevents at the server may be interpreted as a vehicle related eventaltogether. An exemplary access control unit event may be related todetection of the vehicles with the vehicle sensors 714 (FIG. 13). Thisdata must be accurately transferred to the system server 603 along withthe user related event data.

As shown in FIG. 13, in one embodiment of the access control station700, both the checkpoint monitor 602A and the access control unit 702may be supported by a base 704 so that the access control unit 702 maybe made an integral part of the check point monitor 602A to facilitatemonitoring of vehicles as well as users of the compliance monitoredfield. A connection line 713 electronically connects the check pointmonitor 602A to the access control unit 703. As described in theprevious embodiments, the checkpoint monitor may have a head 612A or topsection supported by a body section 612B or a bottom section. The bodysection 612B may include a server and other components of the checkpointmonitor 602A. The access control unit 702 may include a housing 706supported by a post 708. The housing 706 may include a drive or motorand other inner components to operate the access control unit 702. Analert member 710 may be movably attached to the drive 712, which may bean electric motor. In one embodiment the alert member 710 may be abarrier arm, which will be referred to as barrier 710 hereinafter.

As seen in FIG. 13, the barrier 710 extends generally along the Ydirection over the access location 606 that generally extends alongX₁-X₂ direction, when both the checkpoint monitor 602A and the accesscontrol unit are maintained in vertical position, along Z direction, onthe base 704.

The drive 712 may be configured to pivot the barrier 710 between ablocking position ‘A1’, or closed position, for example a horizontalposition, and an open position ‘A2’, for example a vertical position.The blocking position ‘A1’ of the barrier 710 is for alerting vehiclesto stop vehicles at the access control station 700 for check in or checkout process, for example, at the border of the compliance monitoredfield. The barrier 710 is moved into the open position ‘A2’ so that thevehicle may enter or exit the hydrocarbon wellsite and to indicate thatat least a user in the vehicle is successfully authenticated by thecompliance monitoring system 600.

The barrier 710 of the access control unit 702 may be used as a physicaland visible indicator of the access control station 700 to alert vehicledrivers to the presence of the access control station 700 and make themstop. The barrier 710 may not be for restricting vehicles or individualsentering or exiting the monitored location 601. Further the barrier 710may not be for controlling vehicle traffic in to or out of the monitoredlocation 601.

The access control unit 702 may include vehicle sensors 714, forexample, a first sensor 714A and second sensor 714B to detect vehiclesapproaching the access control station 700. The first sensor 714A may bealigned toward the X₁ direction to detect vehicles entering themonitored location 601, and the second sensor 714B may be aligned towardthe X₂ direction to detect vehicles exiting the monitored location 601.For safety reasons, the access control unit 702 may not open the barrier710 if a vehicle has not been detected by either vehicle sensors evenwhen a valid user operation is occurred, e.g., a user is authenticated.When a vehicle detection triggers the access control unit 702 to movethe barrier in the open position A2 (not emergency or fault state), thesensor input allows access control unit 702 to keep the barrier 710 inthe open position A2, or reverse the barrier movement to the openposition A2 if the barrier 710 is moving toward the blocking positionA1, until no vehicle is detected. When no vehicle is detected, thebarrier is moved to the blocking position A1 after a configurable delay.The vehicle sensors 714 may include radar sensors using radar technologythat do not require a reflective object for reference and the distanceand sensitivity are adjustable. Radar based sensors are ideal in orderto simplify deployments and adapt to a variety of locations compared totraditional fixed access control unit systems where several hardwireddetection loops are buried underground at the vehicle detection areas.Alternative vehicle sensing and recognition systems may also be includedwith the access control unit 702. They may include artificialintelligence for vehicle recognition on the captured screenshots of thevehicle, or by adding cameras for License Plate Reading (LPR)capabilities.

During an emergency, a stop switch 716 or an interlock (not shown) maybe activated to maintain the barrier in the open position A2indefinitely, until it is switched off. The stop switch may be used foremergencies or under exceptional operational conditions to allow allvehicle traffic to flow freely. For non-emergencies, a single-time opencommand may be issued by a manual bypass such as using a keypad 718which may be only activated by a numeric code by authorized personnel.

Status of the access control unit 702 may be audibly and visuallycommunicated to the drivers by color coded light indicators and buzzers.When the barrier 710 is ready for closing, buzzer may be activated as awarning for users around the access location 606. When the emergencystop switch 716 is activated, there may be a temporary audiblenotification.

The barrier 710 may be telescopic so that the length of the barrier 710may be adjustable on location to fit the access road width and toexpedite installation. The barrier 710 may be made of a light material,such as aluminum or aluminum alloys, that may be breakable to preventany vehicle damage if an accidental collision occurs. Furthermore, amounting component (not shown) coupling the barrier 710 to the accesscontrol unit 702 may have break-away capabilities so that the barrier710 separates from the access control unit 702 during an accidentalcollision.

The head section 612A of the checkpoint monitor 602A may comprise aplurality of cameras 614 and a plurality of presence sensors 616 forhaving 360 degrees image capture and sensing capability. A display 618may display various status related information in use. Warning and guidelights 617 may give users visual warnings for valid and invalidoperations in checking in to the monitored location 601 or checking outof it with or without a vehicle. Warning and guide lights 617 may alsobe used to provide feedback to the users. If a vehicle is detected, thelight feedback may be a vehicle sign and when no vehicle is detected thelight feedback may be a walking user sign.

The body section 612B may contain critical inner components of thecheckpoint monitor 602A, such as a server 630 (FIG. 16) having aprocessor, a data storage and a control software with various modules,power connections and/or power supply, various communication, datacapture and detection hardware and the like devices.

In this embodiment, the checkpoint monitor 602A may include an RFreceiver, a keypad 718 or numerical keypad and a barcode reader 720 toreceive an access code which is associated with the user's identity, whoattempts to enter or exit the monitored location 601.

As previously described, the access code may comprise a useridentification (ID) code component and a user activity code component,which may be used to determine user's assignment status and activitystatus by the checkpoint monitor. The received access code is used toauthenticate the user, i.e., the user's assignment status and the user'sactivity status.

The user ID code may be a unique number or barcode associated with theuser who is authorized to use the access code. The user activity codemay identify an activity status of the user as to whether the user ischecking in or out. The checkpoint monitor 602A may analyze the user IDcode and the user activity code of the access code to determine user'sassignment status and activity status.

An access code provider device or access code provider may be used todeliver an access code in various forms to the access control station700. In this embodiment, examples of the access code providers may be anaccess code device 642, a keypad 718 and a user ID card 721 having abarcode 723, as shown in FIGS. 14A-14C.

As described above with respect to FIG. 4, and shown in FIG. 14A, theaccess code associated with the user's identity may be transmitted as anaccess code signal 641 using the access code device 642. The access codesignal may be an RF signal and the access code device 642 may be an RFsignal transmitter. The access code signal 641 may be received by the RFreceiver 717 on the checkpoint monitor 602A. The access code signal 641may include both the user ID code and the user activity code, which areused to determine user's assignment status and activity status. The useractivity code may be manually selected on the access code device 642 bythe user.

As shown In FIG. 14B, using the keypad 718, however, a user may type ina numerical code, which includes the access code. The typed in numericaccess code may include both the user ID code and the user activitycode, which are used to determine user's assignment status and activitystatus.

As shown in FIG. 14C, the access code may be the barcode 723 on the userID card 721 identifying the user. A first side 721A of the user ID card721 may include the barcode 723A including the user ID code and the useractivity code for checking in to the monitored location 601. A secondside 721B of the user ID card 721 may include the barcode 723A includingthe user ID code and the user activity code for checking out of themonitored location 601.

The RF receiver 717, the keypad 718 and the barcode reader 720 may allbe integral parts of the checkpoint monitor 602A and may be connected tothe access module of the checkpoint monitor (not shown). The accessmodule 140A of the checkpoint monitor 102 is shown in FIG. 4, as anexample.

In an alternative embodiment, the keypad 718 may be integrated with theaccess control unit 702 rather than the checkpoint monitor. Besidesusing it for access code entry, the keypad 718 may also be used toperform certain bypass functions to independently operate the accesscontrol unit 702 without the checkpoint monitor's involvement. Thisparticular feature of the keypad 718 may be desired especially at theinstallment stage of the access control station 700 before establishingany connection between the checkpoint monitor 602A and the accesscontrol unit 702. Once the checkpoint monitor 602A and the accesscontrol unit 702 are connected, the keypad 718 may be used for accesscode entry function as explained above.

FIGS. 15A and 15B show the base plates 704A-704D of the base 704 of theaccess control station 700. The checkpoint monitor 602A and the accesscontrol unit 702 may be mounted to a first base plate 704A and a secondbase plate 704B respectively as separate parts of the access controlstation 700. This may enable easy equipment deployment and removal by asingle technician since the weight is manageable across the separateparts. The base 704 may be formed by joining the first and second baseplates 704A and 704B together by bolting them to a first linking plate704C and a second linking plate 704D when installing the access controlstation 700 at the monitored location 601. The linking plates arefastened on top of the independent plates to mechanically integrate theaccess control unit 702 and the checkpoint monitor 602A as a singlepiece while providing increased surface area and weight for stability ofthe barrier operation. Irregularities of the installation surface can becompensated by adjusting elevation with the same fastening mechanism.

FIG. 16 shows components of the compliance monitoring system 600. In thehousing 706, the access control unit 702 may include a control module703, or a controller, which is in communication with the processor 634of the checkpoint monitor 602A via an access control unit module 640 ora module 640 which may be a network switch connecting the electronics ofthe access control unit 702 to the checkpoint monitor 602A.Particularly, when the access control unit 702 is connected to thecheckpoint monitor 602A via the module 640, the control module 703 ofthe access control unit may become part of the internal network of thecheckpoint monitor 602A.

The control module 703 may be in connection with the drive 712 (barrierdrive), the vehicle sensors 714, the stop switch 716, the warning system719, and a wireless remote receiver 722 with an antenna 722A. Thecontrol module 703 may be configured to operate the drive 712 forpivoting the barrier 710 between the blocking position A1 and the openposition A2. The control module 703 may provide real time status data tothe checkpoint monitor 602A as the control module 703 receives data fromthe above identified components of the access control unit 702. Thewireless remote receiver 722 may be used to operate the barrier 710 by auser activated wireless remote device (not shown). The control module703 may receive commands from other devices such as the keypad 718. Theaccess control unit 702 may have an emergency battery backup system 724to open the barrier upon a power loss event and to reverse automaticallyif the drive 712 requires power to close the barrier 710.

The access control unit 702 collects and transmits status informationand receives commands from the checkpoint monitor via the internalnetwork. The user data provided by the client organizations, individualcheckpoint monitors, access control stations and other data sources maybe stored in a system data storage 650 by a system processor 652 of thesystem server 603. The data may be received and sent via a firstcommunication module 656A and a second communication module 656B.Various components of the system server 603 and their operation orfunctions and its location details are similar to the componentsincluded in the system server 103 described above with respect to FIG.5. For clarity, other components of the system server 103 are notincluded and new reference numerals are used in the exemplary systemserver 603 shown FIG. 15. Differing from the checkpoint monitor 102described, for example, with respect to FIG. 4, the checkpoint monitor602A may include the module 640 to operate the access control unit 702via the control module 703. Data related to vehicle events and userevents, which are provided by the access control unit 702 and thecheckpoint monitor 602A, may be stored in the storage unit 632 andtransmitted to the system server 603 via the communication module 636.Similarly the user data and the related vehicle data may be receivedfrom the system server and stored in the data storage 632.

FIGS. 17A-17C exemplifies an embodiment of a method of the presentinvention. As shown in FIG. 17A, an exemplary operation may begin withthe barrier 710 placed in the blocking position A1. As a vehicle 730approaches to the access control station 700, signs nearby may instructa user 732 (driver) to move the vehicle closer until the first vehiclesensor 714A detects the vehicle 730. Once the vehicle is detected, ared-light indicator may prompt the user 732 to stop the vehicle 730before the access control station 700 and to use access code to open thebarrier 710. For safety, the barrier 710 may be kept in the blockingposition A1 when no vehicle is detected by the vehicle sensors 714, evenwhen the access code is valid. The detection of an access code includingaccess code signal, barcode access code, valid numeric code, wirelessremote and emergency stop activations are registered to the systemserver 603 as events independently of the barrier open/close action.

As shown in FIG. 17B, once access code is processed and the user 732 inthe vehicle 730 is authenticated by the system, the barrier 710 is movedinto open position A2. The access code details are recorded in thecheckpoint monitor 602A. If an access code is not used, any manualmethod to open the barrier is also recorded as events. When the barrier710 opens, a green-light indicator may be visible. The barrier 710 mayremain in the open position and the green light may stay on as long asthe vehicle 730 is detected on the area monitored by the vehicle sensors714 without any time limit.

As shown in FIG. 17C, once the vehicle 730 moves out of the range of thesecond sensor 714B, an audible alert may be activated for a few secondsto alert the users that the barrier is about to close. Then, the barrieris moved into the closed position A1 and the access control unit 702returns to idle state. If no vehicle is detected by the vehicle sensors714, the users of the monitored location 601 can check in and check outas usual and the user events are registered by the checkpoint monitor602A. Next, all the events registered for this vehicle entry, i.e., theuser related events or data and the vehicle events, may be transmittedto the system server 603 for compliance monitoring of this vehicleentry. Of course, the same steps described in FIG. 17A through 17C mayhappen at the access control station 700 when the user 732 and theassociated vehicle 730 exit the monitored location, and this data isalso reported to the system server 603 for compliance monitoring. Whenno vehicle is detected, to avoid any accidents, the barrier is notopened or closed during the check in or check out of the users.

FIG. 18 is a flowchart 740 illustrating, in one embodiment of the system600, an exemplary compliance monitoring algorithm that monitors accessto the monitored location 601 using the access control station 700,installed at the access location 606, in connection with the systemserver 603.

Referring to FIGS. 12A-12B, 13, 14A-14C, 16, 17 and 18, in step 740A,the vehicle 730 may be detected by the vehicle sensors 714 on the accesscontrol unit 702 and, via the control module 703 of the access controlunit 702. Next, a vehicle detection signal including vehicle detectiondata may be transmitted to the checkpoint monitor 602A from the accesscontrol unit 702, in step 740B, which places the checkpoint monitor 602Ain a standby mode to receive an access code from the user 732 (driver oran occupant) of the vehicle 730.

In step 740C, the processor 634 may authenticate the user, i.e., theuser's ID and/or the status, by analyzing the access code that isreceived by the checkpoint monitor 602A depending on the selected methodof access code delivery. As described above with respect to FIG. 13 andFIGS. 14A-14C, the user 732 may deliver a user access code assigned tohim/her using several ways, for example: by transmitting it from a useraccess code device, introducing as barcode or typing it in as a numericcode.

In step 740D, if the user cannot be authenticated, the checkpointmonitor 602A of the access control station 700 may report the event asan invalid operation in step 740E to the system server 603 of themonitoring center. Authentication of a user's assignment status andactivity status was explained in detail with respect to FIG. 9 above. Ifthe user is authenticated in step 740D, the processor 634 of thecheckpoint monitor 602A approves/updates the assignment status of theuser and updates the activity status of the user as described above.Next, in step 740F, the processor 634 commands the control module 703 ofthe access control unit 702 to move the barrier 710 from the blockingposition A1 to the open position A2. In response, the control module 703operates the drive 712 to pivot the barrier 710 to the open position A2to allow the vehicle 730 to enter the monitored location 601. In step740G, if the vehicle sensors 714 continue to detect the vehicle 730, thebarrier 710 is maintained in the open position A2. If the vehiclesensors 714 no longer detect the vehicle 730, the barrier 710 may bepivoted to the blocking position A1 in step 740H. Next, prior to step740H or after step 740H, the checkpoint monitor 602A may transmit thevehicle status data, including the vehicle detection data and other datareceived from the access control unit, and the associated user'sassignment status and activity status to the system server 603 forcompliance monitoring.

Although aspects and advantages of the present invention are describedherein with respect to certain preferred embodiments, modifications ofthe preferred embodiments will be apparent to those skilled in the art.Thus, the scope of the present invention should not be limited to theforegoing discussion, but should be defined by the appended claims.

We claim:
 1. A system for compliance monitoring of vehicles and users ofhydrocarbon wellsites, the system comprising: a system server includinga system data storage and a system processor; a portable access controlstation located in a hydrocarbon wellsite which is a compliancemonitored hydrocarbon wellsite and remotely located from the systemserver; a checkpoint monitor of the portable access control station, thecheckpoint monitor including a server having a data storage and aprocessor in communication with the system processor; an access controlunit of the portable access control station, the access control unitbeing in communication with the server of the checkpoint monitor andincluding vehicle sensors to detect vehicles, a barrier drive which ismovably coupled to a vehicle barrier, and a controller configured to bein connection with the processor of the server, the vehicle sensors andthe barrier drive, the controller being configured to operate thebarrier drive for pivoting the vehicle barrier between a blockingposition and an open position; wherein upon receiving vehicle sensordata from the vehicle sensors indicating the presence of a vehicle, theprocessor analyzes an access code received from an access code providerto authenticate a user in the vehicle and signal the controller of theaccess control unit to move the vehicle barrier into the open positionto allow the vehicle to enter the hydrocarbon wellsite when the user issuccessfully authenticated, and wherein the access code includes a userID code and a user activity code.
 2. The system of claim 1, wherein thedata storage stores a control program that when executed causes theprocessor to operate the checkpoint monitor.
 3. The system of claim 2,wherein an assignment data table is stored in the data storage, theassignment data table including a user assignment status data and a useractivity status data.
 4. The system of claim 3, wherein whenauthenticating the user, the processor is configured to analyze theaccess code to authenticate both a user assignment status using the userID code of the access code and a user activity status using the useractivity code of the access code.
 5. The system of claim 4, wherein theauthentication of the user assignment status identifies the user on theassignment data table.
 6. The system of claim 5, wherein theauthentication of the user activity status updates a user activitystatus data on the assignment data table as to whether the user is in acheck in activity to enter the hydrocarbon wellsite or in a check outactivity to exit the hydrocarbon wellsite.
 7. The system of claim 1,wherein the checkpoint monitor includes a RF detector to receive theaccess code.
 8. The system of claim 7, wherein the access code provideris an RF transmitter device to transmit the access code as an RF signalto be received by the RF detector.
 9. The system of claim 1, wherein theaccess code provider is a keypad to type in the access code, the key padbeing attached to the portable access control station.
 10. The system ofclaim 1, wherein the checkpoint monitor includes a barcode reader. 11.The system of claim 10, wherein the access code provider is a user IDcard including a barcode having the access code.
 12. The system of claim6, wherein the checkpoint monitor transmits the user assignment statusand the user activity status to the system server along with the vehiclesensor data from the vehicle sensors after authenticating the user. 13.A method for compliance monitoring of vehicles and users of hydrocarbonwellsites, comprising: providing a system server in a monitoring center,the system server including a system processor and a system data storageincluding an assignment data table for the monitored location and asystem program that when executed causes the system processor to operatethe system, wherein the assignment data table includes user assignmentstatus data and user activity status data; installing a checkpointmonitor on a perimeter of a hydrocarbon wellsite which is compliancemonitored and remotely located from the system server, the checkpointmonitor including a processor and a data storage including theassignment data table received from the system server and a program thatwhen executed causes the processor to operate the checkpoint monitor;installing an access control unit adjacent the checkpoint monitor, theaccess control unit including vehicle sensors to detect vehicles, abarrier drive which is movably coupled to a vehicle barrier, and acontroller being in connection with the processor of the checkpointmonitor, the vehicle sensors and the barrier drive; detecting a vehiclewith the vehicle sensors of the access control unit; receiving, in thecheckpoint monitor, vehicle sensor data from the access control unitindicating presence of a vehicle; receiving, in the checkpoint monitor,an access code from an access code provider operated by a userassociated with the vehicle; analyzing with the processor the accesscode received from the access code provider to authenticate the userassociated with the vehicle; pivoting the vehicle barrier from ablocking position to an open position using the barrier drive to allowthe vehicle to enter the hydrocarbon wellsite upon successfullyauthenticating the user associated with the vehicle; receiving, in thecheckpoint monitor, vehicle sensor data from the access control unitindicating absence of a vehicle; and pivoting the vehicle barrier fromthe open position to the blocking position using the barrier drive. 14.The method of claim 13, wherein authentication of the user includesdetermining a user assignment status by authenticating a user identifierincluded in the access code against the user assignment status data onthe assignment data table stored in the data storage of the checkpointmonitor.
 15. The method of claim 14, wherein authentication of the userincludes determining a user activity status by updating the useractivity status data on the assignment data table by utilizing anactivity status identifier in the access code to provide that the useris either in a check in activity to enter the hydrocarbon wellsite or ina check out activity to exit the hydrocarbon wellsite.
 16. The method ofclaim 15 further comprising transmitting, from the check point monitorto the system server, the user assignment status and the user activitystatus along with the vehicle sensor data after authenticating the user.17. The method of claim 13, wherein the access code provider is an RFtransmitter device to transmit the access code as an RF signal to bereceived by an RF detector of the checkpoint monitor.
 18. The method ofclaim 13, wherein the access code provider is a key pad to type in theaccess code, the key pad being attached to the access control unit. 19.The method of claim 13, wherein the access code provider is a user IDcard including a barcode having the access code.
 20. The method of claim19, wherein the barcode having the access code is read by a barcodereader on the checkpoint monitor.